Instead of writting the same test multiple times only because a single parameter is different, we can use @ParameterizedTest providing an input source with the different input/expected values.

On the other hand, consider to use randomString() when the value "is not important" and our code accepts whatever value, it could raise up hidden bubs in our code (hardcoded values, default behavior given a default value, ...)

I didn't want to write a @ParameterizedTest for just 2 tests because I thought it would reduce the readability a bit. But I can change it anyway, since I will change some of the values with randomString()

Are we only testing when the response is empty?
Should we test other cases?
As commented on another comment, we can use @ParameterizedTest on that case.

What about creating a Mother method to easily create Request with custom value?

Looks like we are only testing the case where arguments are the same

Each method is actually covered with 3 tests:

• same arguments, at the same time
• same arguments, called sequentially
• different arguments, at the same time

Instead of hardcoded values, we should use random ones.
On the other hand, QueryChannelRequest constructor is generating an "equal" instance, but we should verify it by initializing it with custom data, not only the default values.